-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resolve proc override paths in var values #1981
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this seems to kind of be based on faulty assumptions. is baystation even on 515 yet?
/atom/movable/proc/foo() | ||
return | ||
|
||
/datum/var/bar = /atom/movable/foo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this errors in DM, it's invalid (tries to find a type rather than a proc)
in 515 and later the proper way to call the latest override (lateral or descended) is via call(nameof(/atom/movable/proc/foo))()
(or call(nameof(/atom/movable.proc/foo))()
, i don't know why that one is sometimes used? i think it's just a legacy thing)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Repeating what I said on discord a while back (to keep any PR observers informed), this does work if it's a proc override. My mistake was not erroring when there's no proc override declared.
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
Gets bay compiling when some of my other PRs are also merged.
Also changes procpaths with
/proc/
elements to point at the original declaration, not lateral overrides. In this case a new pragma is emitted if lateral overrides exist.